High voltage distribution systems and methods

ABSTRACT

Provided in this disclosure is a high voltage distribution system of an electric aircraft. The system includes a power source mechanically connected to an electric aircraft, where the power source is configured to supply power to the electric aircraft. The system also includes a flight component mechanically connected to the electric aircraft. The system also includes a distribution component configured to control the providing of power to and from the power source and the flight component as needed during recharging and/or operation of the electric aircraft.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of Non-provisional application Ser. No. 17/529,710 filed on Nov. 18, 2021 and entitled “HIGH VOLTAGE DISTRIBUTION SYSTEMS AND METHODS,” the entirety of which is incorporated herein by reference.

FIELD OF THE INVENTION

The present invention generally relates to the field of aircraft. In particular, the present invention is directed to high voltage distribution systems and methods of an electric aircraft.

BACKGROUND

Aviation is a perpetually evolving field. However, challenges in modern flight continue to pose difficulties in regard to efficient operation and control of aircraft.

SUMMARY OF THE DISCLOSURE

In an aspect, a high voltage distribution system is provided. The system includes: a power source mechanically connected to an electric aircraft, wherein the power source is configured to supply power to the electric aircraft. The system also includes a flight component mechanically connected to the electric aircraft. The system includes a high voltage distribution component. The high voltage distribution component that includes a power source connection configured to electrically connect the power source and the high voltage distribution component. The high voltage distribution component also includes a flight component connection configured to electrically connect the flight component and the high voltage distribution component. The high voltage distribution component includes a controller, wherein the controller is configured to: provide power to the power source from an electric charger via the battery connection; and provide electrical power to the flight component from the power source via the flight component connection. Additionally, the high voltage distribution component includes a multibus configured to supply power from the power source to the flight component.

In another aspect, a method for high voltage distribution for an electric aircraft is provided. The method includes providing a high voltage distribution system. The high voltage system comprises at least a power source, a flight component, and a high voltage distribution component. The high voltage distribution component that includes a power source connection configured to electrically connect the power source and the high voltage distribution component. The high voltage distribution component also includes a flight component connection configured to electrically connect the flight component and the high voltage distribution component. The high voltage distribution component includes a controller, wherein the controller is configured to: provide power to the power source from an electric charger via the battery connection; and provide electrical power to the flight component from the power source via the flight component connection. Additionally, the high voltage distribution component includes a multibus configured to supply power from the power source to the flight component. The method also includes determining, by the controller, an actuating power input of the flight component. The method also includes supplying, by the high voltage distribution component, an actuating power correlated to the actuating power input to the flight component from the power source via a flight component connection between the high voltage distribution component and the flight component.

These and other aspects and features of non-limiting embodiments of the present invention will become apparent to those skilled in the art upon review of the following description of specific non-limiting embodiments of the invention in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

For the purpose of illustrating the invention, the drawings show aspects of one or more embodiments of the invention. However, it should be understood that the present invention is not limited to the precise arrangements and instrumentalities shown in the drawings, wherein:

FIG. 1 is a diagrammatic representation of an exemplary embodiment of a high voltage distribution system of an aircraft in one or more aspects of the present disclosure;

FIG. 2 is a diagrammatic representation of an exemplary embodiment of an aircraft in one or more aspects of the present disclosure;

FIG. 3 is a block diagram of an exemplary embodiment of a method for high voltage distribution for an electric aircraft in one or more aspects of the present disclosure;

FIG. 4 is a block diagram of an exemplary embodiment of a flight controller in one or more aspects of the present disclosure; and

FIG. 5 is a block diagram of a computing system that can be used to implement any one or more of the methodologies disclosed herein and any one or more portions thereof.

The drawings are not necessarily to scale and may be illustrated by phantom lines, diagrammatic representations and fragmentary views. In certain instances, details that are not necessary for an understanding of the embodiments or that render other details difficult to perceive may have been omitted.

DETAILED DESCRIPTION

At a high level, aspects of the present disclosure are directed to an aircraft configured to provide safe and robust power distribution operations. More specifically, high voltage distribution systems and methods are provided. In one or more embodiments, the system may include a high voltage distribution component having a multibus, which provides redundancy and the elimination of single point failures, such as failure in operation of a flight component due to loss of power, that can make the electric aircraft non-operable in flight. Utilization of a controller, desirably, further adds to the operational safety and control of the high voltage distribution by transferring power to and from various components of the electric aircraft and/or system at varying levels. Exemplary embodiments illustrating aspects of the present disclosure are described below in the context of several specific examples.

In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, that the present invention may be practiced without these specific details. As used herein, the word “exemplary” or “illustrative” means “serving as an example, instance, or illustration.” Any implementation described herein as “exemplary” or “illustrative” is not necessarily to be construed as preferred or advantageous over other implementations. All of the implementations described below are exemplary implementations provided to enable persons skilled in the art to make or use the embodiments of the disclosure and are not intended to limit the scope of the disclosure, which is defined by the claims. For purposes of description herein, the terms “upper,” “lower”, “left”, “rear”, “right”, “front”, “vertical”, “horizontal”, “upward”, “downward”, “forward”, “backward” and derivatives thereof shall relate to the invention as oriented in FIG. 2 . Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary or the following detailed description. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply exemplary embodiments of the inventive concepts defined in the appended claims. Hence, specific dimensions and other physical characteristics relating to the embodiments disclosed herein are not to be considered as limiting, unless the claims expressly state otherwise.

Referring now to FIG. 1 , an exemplary embodiment of a high voltage distribution system 100 for an electric aircraft 104 is shown in accordance with one or more embodiments of the present disclosure. In one or more embodiments, high voltage distribution system 100 includes a power source 108, which is mechanically connected to electric aircraft 104. In one or more embodiments, power source 108 is configured to store and provide an electrical charging current. As used in this disclosure, a “power source” is a source of electrical power, such as, for example, a battery pack 112. As used in this disclosure, an “electrical charging current” is a flow of electrical charge that facilitates an increase in stored electrical energy of an energy storage, such as without limitation a battery. In one or more non-limiting embodiments, power source 108 may be configured to store a range of electrical energy between approximately 5 KWh and about 5,000 KWh. Power source 108 may house a variety of electrical components.

In one or more embodiments, power source 108 is configured to supply power to the electric aircraft 104 and/or subsystems thereof for operation. In one or more embodiments, power source 108 may include a plurality of battery packs. For example, as shown in FIG. 1 , power source 108 may include five battery packs mounted to electric aircraft 104. In one or more embodiments, battery pack may store power and/or supply power to electric aircraft 104 and/or subsystems thereof for operation. In one or more embodiments, battery pack 112 may include a plurality of battery modules, such as modules. For example, and without limitation, battery pack 112 may include fourteen battery modules. In one or more embodiments, each battery module may include a battery cell. For example, and without limitation, a battery module may include a plurality of battery cells. Battery pack 112 may be configured to store electrical energy in the form of a plurality of battery modules, which themselves include of a plurality of battery cells, such as electrochemical cells. These cells may utilize electrochemical cells, galvanic cells, electrolytic cells, fuel cells, flow cells, pouch cells, and/or voltaic cells. In general, an electrochemical cell is a device capable of generating electrical energy from chemical reactions or using electrical energy to cause chemical reactions, this disclosure will focus on the former. Voltaic or galvanic cells are electrochemical cells that generate electric current from chemical reactions, while electrolytic cells generate chemical reactions via electrolysis. In general, the term “battery” is used as a collection of cells connected in series or parallel to each other. A battery cell may, when used in conjunction with other cells, may be electrically connected in series, in parallel or a combination of series and parallel. Series connection includes wiring a first terminal of a first cell to a second terminal of a second cell and further configured to include a single conductive path for electricity to flow while maintaining the same current (measured in Amperes) through any component in the circuit. A battery cell may use the term “wired,” but one of ordinary skill in the art would appreciate that this term is synonymous with “electrically connected”, and that there are many ways to couple electrical elements like battery cells together. An example of a connector that does not include wires may be prefabricated terminals of a first gender that mate with a second terminal with a second gender. Battery cells may be wired in parallel. Parallel connection includes wiring a first and second terminal of a first battery cell to a first and second terminal of a second battery cell and further configured to include more than one conductive path for electricity to flow while maintaining the same voltage (measured in Volts) across any component in the circuit. Battery cells may be wired in a series-parallel circuit which combines characteristics of the constituent circuit types to this combination circuit. Battery cells may be electrically connected in a virtually unlimited arrangement which may confer onto the system the electrical advantages associated with that arrangement such as high-voltage applications, high-current applications, or the like. In an exemplary embodiment, and without limitation, battery pack 112 include 196 battery cells in series and 18 battery cells in parallel. This is, as someone of ordinary skill in the art would appreciate, is only an example and battery pack 112 may be configured to have a near limitless arrangement of battery cell configurations. Battery pack 100 may be designed to the Federal Aviation Administration (FAA)'s Design Assurance Level A (DAL-A), using redundant DAL-B subsystems.

In one or more embodiments, battery modules may be wired together in series and in parallel. Battery pack 112 may include a center sheet which may include a thin barrier. The barrier may include a fuse connecting battery modules on either side of the center sheet. The fuse may be disposed in or on the center sheet and configured to connect to an electric circuit comprising a first battery module and therefore battery unit and cells. In general, and for the purposes of this disclosure, a fuse is an electrical safety device that operate to provide overcurrent protection of an electrical circuit. As a sacrificial device, its essential component is metal wire or strip that melts when too much current flows through it, thereby interrupting energy flow. The fuse may include a thermal fuse, mechanical fuse, blade fuse, expulsion fuse, spark gap surge arrestor, varistor, or a combination thereof.

In other embodiments, battery pack 112 may include a battery management component. For example, battery pack 112 may include a pack monitoring unit (PMU) and a module monitor unit (MMU) to detect and transmit datum related to power characteristics of battery pack 112, which may acquire power metrics datum about battery pack 112. An MMU of a battery management component may use a sensor to detect power characteristics of battery pack 112, or components thereof, which the MMU and/or a PMU may use to generate power source metrics datum to transmit to a controller of system 100, as discussed further below in this disclosure. Battery pack may be consistent with disclosure of battery pack in U.S. patent application Ser. No. 17/529,653 and titled “AN ELECTRIC AIRCRAFT BATTERY PACK AND METHODS OF USE”, which is incorporated herein by reference in its entirety.

Still referring to FIG. 1 , system 100 includes a flight component 116, which is mechanically connected to electric aircraft 104. As used in this disclosure a “flight component” is a portion of an aircraft that can be moved or adjusted to affect one or more flight elements, or movement in a fluid medium. For example, flight component 116 may include a component used to affect the aircraft's roll, yaw, or pitch. In one or more embodiments, flight component 116 may include a plurality of flight components. In an embodiment, flight component 116 may be mechanically connected or otherwise attached to an aircraft. As used herein, a person of ordinary skill in the art would understand “mechanically connected” to mean that at least a portion of a device, component, or circuit is connected to at least a portion of the aircraft via a mechanical coupling. Said mechanical coupling can include, for example, rigid coupling, such as beam coupling, bellows coupling, bushed pin coupling, constant velocity, split-muff coupling, diaphragm coupling, disc coupling, donut coupling, elastic coupling, flexible coupling, fluid coupling, gear coupling, grid coupling, hirth joints, hydrodynamic coupling, jaw coupling, magnetic coupling, Oldham coupling, sleeve coupling, tapered shaft lock, twin spring coupling, rag joint coupling, universal joints, or any combination thereof. In an embodiment, mechanical coupling may be used to connect the ends of adjacent parts and/or objects of an electric aircraft. Further, in an embodiment, mechanical coupling may be used to join two pieces of rotating electric aircraft components.

In one or more embodiments, flight component 116 may include an aerodynamic surface attached to electric aircraft 104 and that interacts with forces to mobilize electric aircraft 104. For example, and without limitation, a flight component may include ailerons, flaps, leading edge flaps, rudders, elevators, spoilers, slats, blades, stabilizers, stabilators, airfoils, a combination thereof, or any other moveable surface used to control an aircraft in a fluid medium.

In other embodiments, flight component may include landing gear. For example, and without limitation, flight component 116 may include skis or wheels attached to a base of a fuselage of electric aircraft 104.

In one or more embodiments, flight component 116 may include a lift component (or lift component assembly), which may include a rotor and a motor 120. Rotor may include blades attached to a hub or may be manufactured as a single piece with an integral hub. Hub may provide a central structure to which blades connect, and in some embodiments, may be made in a shape that envelops motor. Motor may include a rotating part and a stationary part. In one embodiment, rotating part may be concentric to stationary part, known as a radial flux motor. In this embodiment, stationary part may form the outer ring of motor, known as an inrunner motor, or stationary part may form the inner ring of motor, known as an outrunner motor. In other embodiments, rotating and stationary parts may be flat and arranged in opposition to each other, known as an axial flux motor. Rotor may be attached to rotating part of motor. Stationary part of motor, in one embodiment, may be attached to propulsion boom 144. In some embodiments, motor may be a permanent magnet motor and may be controlled by an electronic motor controller. Electronic motor controller may be configured to send electrical currents to motor in a precise sequence to allow rotor to turn at a desired speed or with a desired torque. In some embodiments, this motor controller may be coupled or communicatively connected to flight controller 128 or may be a part of flight controller 128. In one or more embodiments, flight component may include an electrical load 124. For example, and without limitation, a flight component may include a plurality of loads.

In other embodiments flight component 116 may include a propulsion system. For example, and without limitation, flight component may include a propulsor or a lift component. For the purposes of this disclosure, a “propulsor” is a component or device used to propel a craft by exerting force on a fluid medium, which may include a gaseous medium such as air or a liquid medium such as water. Propulsor may include any device or component that consumes electrical power on demand to propel an electric aircraft in a direction or other vehicle while on ground or in-flight. For example, and without limitation, propulsor may include a rotor, propeller, paddle wheel, and the like thereof. In an embodiment, propulsor may include a plurality of blades. As used in this disclosure a “blade” is a propeller that converts rotary motion from an engine or other power source into a swirling slipstream. In an embodiment, blade may convert rotary motion to push the propeller forwards or backwards. In an embodiment, propulsor may include a rotating power-driven hub, to which are attached several radial airfoil-section blades such that the whole assembly rotates about a longitudinal axis. In one or more exemplary embodiments, a propulsor may include a vertical propulsor or a forward propulsor. A forward propulsor may include a propulsor configured to propel electric aircraft 104 in a forward direction. A vertical propulsor may include a propulsor configured to propel electric aircraft 104 in an upward direction. One of ordinary skill in the art would understand upward to comprise the imaginary axis protruding from the earth at a normal angle, configured to be normal to any tangent plane to a point on a sphere (i.e. skyward). In an embodiment, vertical propulsor can be a propulsor that generates a substantially downward thrust, tending to propel an aircraft in an opposite, vertical direction and provides thrust for maneuvers. Such maneuvers can include, without limitation, vertical take-off, vertical landing, hovering, and/or rotor-based flight such as “quadcopter” or similar styles of flight.

In an embodiment, a propulsor may include a propeller, a blade, or the like. The function of a propeller is to convert rotary motion from an engine or other power source into a swirling slipstream which pushes the propeller forwards or backwards. The propulsor may include a rotating power-driven hub, to which are attached several radial airfoil-section blades such that the whole assembly rotates about a longitudinal axis. The blade pitch of a propeller may, for example, be fixed, manually variable to a few set positions, automatically variable (e.g., a “constant-speed” type), or any combination thereof. In an exemplary embodiment, propellers for an aircraft may be designed to be fixed to their hub at an angle similar to the thread on a screw makes an angle to the shaft; this angle may be referred to as a pitch or pitch angle which will determine the speed of the forward movement as the blade rotates.

In an embodiment, a propulsor can include a thrust element which may be integrated into the propulsor. The thrust element may include, without limitation, a device using moving or rotating foils, such as one or more rotors, an airscrew or propeller, a set of airscrews or propellers such as contra-rotating propellers, a moving or flapping wing, or the like. Further, a thrust element, for example, can include without limitation a marine propeller or screw, an impeller, a turbine, a pump-jet, a paddle or paddle-based device, or the like.

Still referring to FIG. 1 , a propulsor may include a pusher component. As used in this disclosure a “pusher component” is a component that pushes and/or thrusts an aircraft through a medium. As a non-limiting example, pusher component may include a pusher propeller, a paddle wheel, a pusher motor, a pusher propulsor, and the like. Pusher component may be configured to produce a forward thrust. As used in this disclosure a “forward thrust” is a thrust that forces aircraft through a medium in a horizontal direction, wherein a horizontal direction is a direction parallel to the longitudinal axis. For example, forward thrust may include a force of 1145 N to force aircraft to in a horizontal direction along the longitudinal axis. As a further non-limiting example, pusher component may twist and/or rotate to pull air behind it and, at the same time, push aircraft 108 forward with an equal amount of force. In an embodiment, and without limitation, the more air forced behind aircraft, the greater the thrust force with which aircraft 108 is pushed horizontally will be. In another embodiment, and without limitation, forward thrust may force aircraft 108 through the medium of relative air. Additionally or alternatively, plurality of propulsor may include one or more puller components. As used in this disclosure a “puller component” is a component that pulls and/or tows an aircraft through a medium. As a non-limiting example, puller component may include a flight component such as a puller propeller, a puller motor, a tractor propeller, a puller propulsor, and the like. Additionally, or alternatively, puller component may include a plurality of puller flight components.

In one or more embodiments, flight component 116 may include a motor 120 and a rotor. Motor may include, without limitation, any electric motor, where an electric motor is a device that converts electrical energy into mechanical energy, for instance by causing a shaft to rotate. A motor may be driven by direct current (DC) electric power; for instance, a motor may include a brushed DC motor or the like. A motor may be driven by electric power having varying or reversing voltage levels, such as alternating current (AC) power as produced by an alternating current generator and/or inverter, or otherwise varying power, such as produced by a switching power source. A motor may include, without limitation, a brushless DC electric motor, a permanent magnet synchronous motor, a switched reluctance motor, and/or an induction motor; persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various alternative or additional forms and/or configurations that a motor may take or exemplify as consistent with this disclosure. In addition to inverter and/or switching power source, a circuit driving motor may include electronic speed controllers (not shown) or other components for regulating motor speed, rotation direction, torque, and/or dynamic braking. In one or more embodiments, motor 144 may include an electromechanical clutch. In one or more embodiments, motor 120 may include a plurality of motors. In one or more embodiments, motor 120 may be mechanically connected to an actuator, which may move flight component 116 upon actuation, which is controlled by motor 120. For example, an actuator may be a lever arm that lifts or lowers an aileron according to a control signal from, for example, a pilot.

In one or more embodiments, motor 120 may include or be connected to one or more sensors detecting one or more conditions of motor 120. One or more conditions may include, without limitation, voltage levels, electromotive force, current levels, temperature, current speed of rotation, position sensors, torque, and the like. For instance, and without limitation, one or more sensors may be used to detect torque, or to detect parameters used to determine torque, as described in further detail below. One or more sensors may include a plurality of current sensors, voltage sensors, speed or position feedback sensors, and the like. A sensor may communicate a current status of motor to a person, operating system or a computing device; computing device may include any computing device as described below, including without limitation, a controller, a processor, a microprocessor, a control circuit, a flight controller, or the like. In one or more embodiments, computing device may use sensor feedback to calculate performance parameters of motor, including without limitation a torque versus speed operation envelope. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various devices and/or components that may be used as or included in a motor or a circuit operating a motor, as used and described herein. In an embodiment, propulsors may receive differential power consumption commands, such as a propeller or the like receiving command to generate greater power output owing a greater needed contribution to attitude control, or a wheel receiving a greater power output due to worse traction than another wheel under slippery conditions.

In one or more embodiments, a rotor may include blades attached to a hub, or may be manufactured as a single piece with an integral hub. Hub may provide a central structure to which blades connect, and in some embodiments, may be made in a shape that envelops motor. Motor may include a rotating part and a stationary part. In one embodiment, rotating part may be concentric to stationary part, known as a radial flux motor. In this embodiment, stationary part may form the outer ring of motor, known as an inrunner motor, or stationary part may form the inner ring of motor, known as an outrunner motor. In other embodiments, rotating and stationary parts may be flat and arranged in opposition to each other, known as an axial flux motor. Rotor may be attached to rotating part of motor. Stationary part of motor, in one embodiment, may be attached to propulsion boom. In some embodiments, motor may be a permanent magnet motor and may be controlled by an electronic motor controller. Electronic motor controller may be configured to send electrical currents to motor in a precise sequence to allow rotor to turn at a desired speed or with a desired torque. In some embodiments, this motor controller may be coupled or communicatively connected to flight controller or may be a part of flight controller.

Still referring to FIG. 1 , system 100 includes a high voltage distribution component 128 (also referred to in this disclosure as a “HV distribution component” or a “distribution component”). In one or more embodiments, distribution component 128 includes a power source connection 132 configured to electrically connect the power source and HV distribution component 128. For the purposes of this disclosure, a “power source connection” is an electrical and/or physical communication between a power source and a high voltage distribution component that allows for transfer of power between the battery pack and the high voltage distribution component. For example, and without limitation, power supplied by a charger 152 through a recharging port may be provided to power source 108 via power source connection 132. In another example, and without limitation, power from power source 108 may be provided to HV distribution component 128 via power source connection.

In one or more embodiments, HV distribution component 128 includes a flight component connection 136 configured to electrically connect flight component 116 and distribution component 128. For the purposes of this disclosure, a “flight component connection” is an electrical and/or physical communication between a flight component and a high voltage distribution component that allows for transfer of power between the flight component and the high voltage distribution component. For example, and without limitation, power supplied by a power source 108 may be provided to flight component 116 via flight component connection 136. In one or more embodiments, flight component connection 136 may include an electrical load 124.

In one or more embodiments, HV distribution component 128 may include a bus. A bus may include various components known in the art, such as a bus master, a bus slave, and/or an intelligent slave. In one or more embodiments, HV distribution component may include a master bus controller. As used in this disclosure a “master bus controller” is one or more devices and/or components that are connected to a bus to initiate a direct memory access transaction, wherein a bus is one or more terminals in a bus architecture. Master bus controller may communicate using synchronous and/or asynchronous bus control protocols. In an embodiment, master bus controller may include flight controller 304. In another embodiment, master bus controller may include one or more universal asynchronous receiver-transmitters (UART). For example, and without limitation, master bus controller may include one or more bus architectures that allow a bus to initiate a direct memory access transaction from one or more buses in the bus architectures. As a further non-limiting example, master bus controller may include one or more peripheral devices and/or components to communicate with another peripheral device and/or component and/or the master bus controller. In an embodiment, master bus controller may be configured to perform bus arbitration. As used in this disclosure “bus arbitration” is method and/or scheme to prevent multiple buses from attempting to communicate with and/or connect to master bus controller. For example, and without limitation, bus arbitration may include one or more schemes such as a small computer interface system, wherein a small computer interface system is a set of standards for physical connecting and transferring data between peripheral devices and master bus controller by defining commands, protocols, electrical, optical, and/or logical interfaces. In an embodiment, master bus controller may receive intermediate representation and/or output language from logic component, wherein output language may include one or more analog-to-digital conversions, low bit rate transmissions, message encryptions, digital signals, binary signals, logic signals, analog signals, and the like thereof described above in detail.

In one or more embodiments, master bus controller may communicate with a slave bus. As used in this disclosure a “slave bus” is one or more peripheral devices and/or components that initiate a bus transfer. For example, and without limitation, slave bus may receive one or more controls and/or asymmetric communications from master bus controller, wherein slave bus transfers data stored to master bus controller. In an embodiment, and without limitation, slave bus may include one or more internal buses, such as but not limited to a/an internal data bus, memory bus, system bus, front-side bus, and the like thereof. In another embodiment, and without limitation, slave bus may include one or more external buses such as external flight controllers, external computers, remote devices, printers, aircraft computer systems, flight control systems, and the like thereof.

In one or more embodiments, a control algorithm may optimize signal communication as a function of determining one or more discrete timings. For example, and without limitation master bus controller may synchronize timing of the segmented control algorithm by injecting high priority timing signals on a bus of the master bus control. As used in this disclosure a “high priority timing signal” is information denoting that the information is important. For example, and without limitation, high priority timing signal may denote that a section of control algorithm is of high priority and should be analyzed and/or transmitted prior to any other sections being analyzed and/or transmitted. In an embodiment, high priority timing signal may include one or more priority packets. As used in this disclosure a “priority packet” is a formatted unit of data that is communicated between the plurality of flight controllers. For example, and without limitation, priority packet may denote that a section of control algorithm should be used and/or is of greater priority than other sections.

In one or more embodiments, HV distribution component 128 may include a multibus. A multibus is a bus architecture that may include an asynchronous bus that accommodates a plurality of independent processors and/or devices operating at various transfer rates (speeds) while maintaining a maximum throughput. In one or more embodiments, multibus may include a ring bus. Ring bus may be consistent with disclosure of ring bus in U.S. patent application Ser. No. 17/528,896 and titled “SYSTEMS AND METHODS FOR BATTERY MANAGEMENT FOR ELECTRIC AIRCRAFT BATTERIES”, which is incorporated herein by reference in its entirety. As used in this disclosure, a “ring bus” is a looped circuit connecting loads and/or power sources in series. High voltage bus 144 may include a ring bus that connects battery packs in series. A multibus may include a multi-master functionality that allows sharing between multiple processors and peripheral devices. In one or more embodiments, multibus of HV distribution component 128 may include a bus tie 156. For example, HV distribution component may include a plurality of bus ties. A bus tie 156 may include an electrical relay configured to automatically and/or manually communicatively connect to a bus. For instance, and without limitation, each bus of a plurality of buses may be connected to a corresponding power source of electric aircraft 104. For example, and without limitation, if a first power source fails, then power from the first power source cannot be provided to a corresponding first bus, which would otherwise distribute power from the first power source to corresponding subsystems of an electrical aircraft, such as a flight component. However, as a result of the detected loss of power to the first bus, bus tie 156 may connect the first bus to a second power source of a second bus so that the second power source is powering both the first bus and the second bus, thus, maintaining power supply to all corresponding flight components of the electric aircraft. In one or more embodiments, the system may include a high voltage distribution component having a multibus, which provides redundancy and the elimination of single point failures, such as failure in operation of a flight component due to loss of power, that can make the electric aircraft non-operable in flight. Utilization of a controller, desirably, further adds to the operational safety and control of the high voltage distribution by transferring power to and from various components of the electric aircraft and/or system at varying levels. Exemplary embodiments illustrating aspects of the present disclosure are described below in the context of several specific examples.

With continued reference to FIG. 1 , a multibus may include a mesh bus. As used in the current disclosure, a “mesh bus” is a conductor or a group of conductor used for collecting electric power from the incoming feeders and distributing the power to the outgoing feeders, wherein the buses are organized in a mesh style formation. In an embodiment, circuit breakers may be installed in the mesh formed by the buses. The circuit may be tapped from the node point of the mesh. A mesh bus arrangement may be controlled by four circuit breakers. When a fault occurs on any section, two circuit breakers may open, resulting in the opening of the mesh. Such type of arrangement provides security against bus-bar fault.

In one or more embodiments, HV distribution component 128 includes a controller 140. In one or more embodiments, controller 140 may be disposed in HV distribution component 128 or be remote to HV distribution component 128. For example, controller 140 may include a flight controller located remotely from HV distribution component 128 in electric aircraft 104. In one or more embodiments, controller 140 may be communicatively connected to battery pack 112 and/or flight components 116. For the purposes of this disclosure, “communicatively connected,” is a process whereby one device, component, or circuit is able to receive data from and/or transmit data to another device, component, or circuit. Communicative connection may be performed by wired or wireless electronic communication, either directly or by way of one or more intervening devices or components. In an embodiment, communicative connection includes electrically connection an output of one device, component, or circuit to an input of another device, component, or circuit. Communicative connection may be performed via a bus, such as multibus 144, or other facility for intercommunication between elements of a computing device. Communicative connection may include indirect connections via “wireless” connection, low power wide area network, radio communication, optical communication, magnetic, capacitive, or optical connection, or the like. In an embodiment, communicative connecting may include electrically connecting an output of one device, component, or circuit to an input of another device, component, or circuit. Communicative connecting may be performed via a bus or other facility for intercommunication between elements of a computing device. Communicative connecting may include indirect connections via “wireless” connection, low power wide area network, radio communication, optical communication, magnetic, capacitive, or optical connection, or the like.

In one or more embodiments, controller 140 may include any computing device as described in this disclosure, including and without limitation, a microcontroller, microprocessor, a flight controller, a digital signal processor (DSP), and/or a system on a chip (SoC) as described in this disclosure. Computing device may include, be included in, and/or communicate with a mobile device such as a mobile telephone or smartphone. Controller 140 may include a single computing device operating independently, or may include two or more computing device operating in concert, in parallel, sequentially or the like; two or more computing devices may be included together in a single computing device or in two or more computing devices. Controller 140 may interface or communicate with one or more additional devices as described below in further detail via a network interface device. Network interface device may be utilized for connecting controller 140 to one or more of a variety of networks, and one or more devices. Examples of a network interface device include, but are not limited to, a network interface card (e.g., a mobile network interface card, a LAN card), a modem, and any combination thereof. Examples of a network include, but are not limited to, a wide area network (e.g., the Internet, an enterprise network), a local area network (e.g., a network associated with an office, a building, a campus or other relatively small geographic space), a telephone network, a data network associated with a telephone/voice provider (e.g., a mobile communications provider data and/or voice network), a direct connection between two computing devices, and any combinations thereof. A network may employ a wired and/or a wireless mode of communication. In general, any network topology may be used. Information (e.g., data, software etc.) may be communicated to and/or from a computer and/or a computing device. Controller 104 may include but is not limited to, for example, a computing device or cluster of computing devices in a first location and a second computing device or cluster of computing devices in a second location. Controller 140 may include one or more computing devices dedicated to data storage, security, distribution of traffic for load balancing, and the like. Controller 140 may distribute one or more computing tasks as described below across a plurality of computing devices of computing device, which may operate in parallel, in series, redundantly, or in any other manner used for distribution of tasks or memory between computing devices. Controller 140 may be implemented using a “shared nothing” architecture in which data is cached at the worker, in an embodiment, this may enable scalability of system 100 and/or computing device.

In one or more embodiments, controller 140 may be designed and/or configured to perform any method, method step, or sequence of method steps in any embodiment described in this disclosure, in any order and with any degree of repetition. For instance, controller 140 may be configured to perform a single step or sequence repeatedly until a desired or commanded outcome is achieved; repetition of a step or a sequence of steps may be performed iteratively and/or recursively using outputs of previous repetitions as inputs to subsequent repetitions, aggregating inputs and/or outputs of repetitions to produce an aggregate result, reduction or decrement of one or more variables such as global variables, and/or division of a larger processing task into a set of iteratively addressed smaller processing tasks. controller 140 may perform any step or sequence of steps as described in this disclosure in parallel, such as simultaneously and/or substantially simultaneously performing a step two or more times using two or more parallel threads, processor cores, or the like; division of tasks between parallel threads and/or processes may be performed according to any protocol suitable for division of tasks between iterations. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various ways in which steps, sequences of steps, processing tasks, and/or data may be subdivided, shared, or otherwise dealt with using iteration, recursion, and/or parallel processing.

In one or more embodiments, controller may generate a control signal to control various components of system 100 and/or process input signals from, for example, power source 108, flight component 116, and/or electric aircraft 104. As used in this disclosure, a “control signal” is an electrical signal that is indicative of information. In some cases, a control signal may include an analog signal or a digital signal. In some cases, control signal may be communicated from one or more sensors, for example located within electric vehicle (e.g., within an electric vehicle battery) and/or located within connector 108. For example, in some cases, control signal may be associated with a battery within an electric vehicle. For example, control signal may include a battery sensor signal. As used in this disclosure, a “battery sensor signal” is a signal representative of a characteristic of a battery. In some cases, battery sensor signal may be representative of a characteristic of an electric vehicle battery, for example as electric vehicle battery is being recharged. In some versions, controller 140 may additionally include a sensor interface configured to receive a battery sensor signal. Sensor interface may include one or more ports, an analog to digital converter, and the like. Controller 140 may be further configured to control one or more of electrical charging current and coolant flow as a function of battery sensor signal and/or control signal. For example, controller 140 may control coolant source and/or power source as a function of battery sensor signal and/or control signal. In some cases, battery sensor signal may be representative of battery temperature. In some cases, battery sensor signal may represent battery cell swell. In some cases, battery sensor signal may be representative of temperature of electric vehicle battery, for example temperature of one or more battery cells within an electric vehicle battery. In some cases, a sensor, a circuit, and/or a controller 104 may perform one or more signal processing steps on a signal. For instance, sensor, circuit, or controller 140 may analyze, modify, and/or synthesize a signal in order to improve the signal, for instance by improving transmission, storage efficiency, or signal to noise ratio.

Exemplary methods of signal processing may include analog, continuous time, discrete, digital, nonlinear, and statistical. Analog signal processing may be performed on non-digitized or analog signals. Exemplary analog processes may include passive filters, active filters, additive mixers, integrators, delay lines, compandors, multipliers, voltage-controlled filters, voltage-controlled oscillators, and phase-locked loops. Continuous-time signal processing may be used, in some cases, to process signals which varying continuously within a domain, for instance time. Exemplary non-limiting continuous time processes may include time domain processing, frequency domain processing (Fourier transform), and complex frequency domain processing. Discrete time signal processing may be used when a signal is sampled non-continuously or at discrete time intervals (i.e., quantized in time). Analog discrete-time signal processing may process a signal using the following exemplary circuits sample and hold circuits, analog time-division multiplexers, analog delay lines and analog feedback shift registers. Digital signal processing may be used to process digitized discrete-time sampled signals. Commonly, digital signal processing may be performed by a computing device or other specialized digital circuits, such as without limitation an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a specialized digital signal processor (DSP). Digital signal processing may be used to perform any combination of typical arithmetical operations, including fixed-point and floating-point, real-valued, and complex-valued, multiplication and addition. Digital signal processing may additionally operate circular buffers and lookup tables. Further non-limiting examples of algorithms that may be performed according to digital signal processing techniques include fast Fourier transform (FFT), finite impulse response (FIR) filter, infinite impulse response (IIR) filter, and adaptive filters such as the Wiener and Kalman filters. Statistical signal processing may be used to process a signal as a random function (i.e., a stochastic process), utilizing statistical properties. For instance, in some embodiments, a signal may be modeled with a probability distribution indicating noise, which then may be used to reduce noise in a processed signal.

In one or more embodiments, controller 140 is configured to provide power to the power source 108 from electric charger 152 via the battery connection. In one or more embodiments, a charger may provide power to battery pack 112 via a recharging port 148 of system 100. In one or more embodiments, port 148 may be mechanically attached to electric aircraft 104. As used in this disclosure, a “port” is an interface for example of an interface configured to receive another component or an interface configured to transmit and/or receive signal on a computing device. For example, in the case of an electric vehicle port, the port interfaces with a number of conductors and/or a coolant flow path by way of receiving a connector. In the case of a computing device port, the port may provide an interface between a signal and a computing device. A connector may include a male component having a penetrative form and port may include a female component having a receptive form, receptive to the male component. Alternatively or additionally, connector may have a female component and port may have a male component. In some cases, connector may include multiple connections, which may make contact and/or communicate with associated mating components within port, when the connector is mated with the port.

In one or more embodiments, power source 108 may receive power from an electric charger via HV distribution component 128. For example, controller 140 may receive and/or determine a charging power input necessary to charge power source 108. Controller 140 may then transmit charging power correlated to the actuating power input to power source 108. HV distribution component may convert and/or alter the rate of power transmitted to power source 108 to suit requirements, such as voltage and/or current, necessary for power source 108 to charge properly.

In one or more embodiments, controller 140 is also configured to supply electrical power to the flight component from power source 108 via the flight component connection. In one or more embodiments, power source 108 may provide power to HV distribution component 128. For example, controller 140 may receive and/or determine an actuating power input necessary to operate flight component 116. Controller 140 may then transmit actuating power correlated to the actuating power input to flight component 116. HV distribution component may convert and/or alter the rate of power transmitted to flight component 116 to suit requirements, such as actuating power, necessary for flight component 116 to operate properly. For example, and without limitation, HV distribution component may output power at a high voltage, at a low voltage, as a direct current, and/or as an alternating current.

In one or more embodiments, power source 108 includes a plurality of battery packs, and flight component 116 includes a plurality of propulsors. In one or more embodiments, a first bus of multibus 144 is configured to supply power from a first power source of the plurality of power sources to a first propulsor of the plurality of propulsors, and a second bus of multibus 144 is configured to supply power from a second power source of the plurality of power sources to a second propulsor of the plurality of propulsors. Bus tie 156 of high voltage distribution component 128 may be configured to initiate a supply of power from the second power source to the first propulsor if the first power source malfunctions.

Referring now to FIG. 2 , an exemplary embodiment of electric aircraft 104 is illustrated in accordance with one or more embodiments of the present disclosure. As used in this disclosure an “aircraft” is any vehicle that may fly by gaining support from the air. As a non-limiting example, aircraft may include airplanes, helicopters, commercial and/or recreational aircrafts, instrument flight aircrafts, drones, electric aircrafts, airliners, rotorcrafts, vertical takeoff and landing aircrafts, jets, airships, blimps, gliders, paramotors, and the like. Electric aircraft 104 may include an electric vertical takeoff and landing (eVTOL) aircraft. Electric aircraft may be capable of rotor-based cruising flight, rotor-based takeoff, rotor-based landing, fixed-wing cruising flight, airplane-style takeoff, airplane-style landing, and/or any combination thereof. Electric aircraft may include one or more manned and/or unmanned aircrafts. Electric aircraft may include one or more all-electric short takeoff and landing (eSTOL) aircrafts. For example, and without limitation, eVTOL aircrafts may accelerate plane to a flight speed on takeoff and decelerate plane after landing. In an embodiment, and without limitation, electric aircraft may be configured with an electric propulsion assembly. Electric propulsion assembly may include any electric propulsion assembly as described in U.S. Nonprovisional application Ser. No. 16/603,225, filed on Dec. 4, 2019, and entitled “AN INTEGRATED ELECTRIC PROPULSION ASSEMBLY,” the entirety of which is incorporated herein by reference.

As used in this disclosure, a vertical take-off and landing (eVTOL) aircraft is an aircraft that can hover, take off, and land vertically. An eVTOL, as used in this disclosure, is an electrically powered aircraft typically using an energy source, of a plurality of energy sources to power aircraft. To optimize the power and energy necessary to propel aircraft 100, eVTOL may be capable of rotor-based cruising flight, rotor-based takeoff, rotor-based landing, fixed-wing cruising flight, airplane-style takeoff, airplane style landing, and/or any combination thereof. Rotor-based flight, as described herein, is where the aircraft generates lift and propulsion by way of one or more powered rotors or blades coupled with an engine, such as a “quad-copter,” multi-rotor helicopter, or other vehicle that maintains its lift primarily using downward thrusting propulsors. “Fixed-wing flight,” as described herein, is where an aircraft is capable of flight using wings and/or foils that generate lift caused by the aircraft's forward airspeed and the shape of the wings and/or foils, such as airplane-style flight.

In one or more embodiments, electric aircraft 104 may include motor 120 (shown in FIG. 1 ), which may be mounted on a structural feature of electric aircraft. Design of motor 120 may enable it to be installed external to the structural member (such as a boom, nacelle, or fuselage) for easy maintenance access and to minimize accessibility requirements for the structure. This may improve structural efficiency by requiring fewer large holes in the mounting area. This design may include two main holes in the top and bottom of the mounting area to access bearing cartridge. Further, a structural feature may include a component of electric aircraft 104. For example, and without limitation structural feature may be any portion of a vehicle incorporating motor 120, including any vehicle as described below. As a further non-limiting example, a structural feature may include without limitation a wing, a spar, an outrigger, a fuselage, or any portion thereof; persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of many possible features that may function as at least a structural feature. At least a structural feature may be constructed of any suitable material or combination of materials, including without limitation metal such as aluminum, titanium, steel, or the like, polymer materials or composites, fiberglass, carbon fiber, wood, or any other suitable material. As a non-limiting example, at least a structural feature may be constructed from additively manufactured polymer material with a carbon fiber exterior; aluminum parts or other elements may be enclosed for structural strength, or for purposes of supporting, for instance, vibration, torque, or shear stresses imposed by at least propulsor 104. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various materials, combinations of materials, and/or constructions techniques.

Now referring to FIG. 3 , a flow chart of an exemplary embodiment of high voltage distribution for electric aircraft 104 is shown. Step 305 of method 300 includes determining, by a controller of a high voltage distribution component, a charging power input of a power source, wherein the power source is mechanically connected to an electrical aircraft. In one or more embodiments, power source 108 may include a module monitor unit (MMU) and pack monitoring unit (PMU) configured to detect, such as via a sensor of the MMU, and communicate a condition of power source 108 to controller 140 of high voltage distribution component 128. For example, and without limitation, an MMU of power source 108 may detect a condition of power source 108, such as a state of charge (SOC), depth of discharge (DOD), voltage rating, current rating, and the like, and transmit the corresponding data to controller so that controller may regulate power received by the charger via port 148 and supplied to power source 108 during recharging.

Step 310 of method 300 includes supplying, by the high voltage distribution component, a charging power correlated to the charging power input to the power source from an electric charger via a power source connection between the high voltage distribution component and the power source. In one or more embodiments, high voltage distribution component 128 includes a recharging port 148, where recharging port 148 is configured to receive power from the charger via port 148.

Step 315 of method 300 includes determining, by the controller, an actuating power input of a flight component. Step 320 includes supplying, by the high voltage distribution component, an actuating power correlated to the actuating power input to the flight component from the power source via a flight component connection between the high voltage distribution component and the flight component. In one or more embodiments, flight component 116 includes electric motor 120, which is configured to convert the electric power from high voltage distribution component 128 into a mechanical movement of flight component 116. In one or more embodiments, power source 108 includes a plurality of battery packs, and flight component 116 comprises a plurality of propulsors. Method 300 may also include supplying, by a first bus of multibus 144 of HV distribution component 128, power from a first power source of the plurality of power sources to a first propulsor of the plurality of propulsors, and supplying, by a second bus of multibus 144, power from a second power source of the plurality of power sources to a second propulsor of the plurality of propulsors. In one or more embodiments, method 300 may further include a bus tie of HV distribution component 128 initiating supply of power from the second power source to the first propulsor if the first power source malfunctions.

Now referring to FIG. 4 , an exemplary embodiment 400 of a flight controller 404 is illustrated. As used in this disclosure a “flight controller” is a computing device of a plurality of computing devices dedicated to data storage, security, distribution of traffic for load balancing, and flight instruction. Flight controller 404 may include and/or communicate with any computing device as described in this disclosure, including without limitation a microcontroller, microprocessor, digital signal processor (DSP) and/or system on a chip (SoC) as described in this disclosure. Further, flight controller 404 may include a single computing device operating independently, or may include two or more computing device operating in concert, in parallel, sequentially or the like; two or more computing devices may be included together in a single computing device or in two or more computing devices. In embodiments, flight controller 404 may be installed in an aircraft, may control the aircraft remotely, and/or may include an element installed in the aircraft and a remote element in communication therewith.

In an embodiment, and still referring to FIG. 4 , flight controller 404 may include a signal transformation component 408. As used in this disclosure a “signal transformation component” is a component that transforms and/or converts a first signal to a second signal, wherein a signal may include one or more digital and/or analog signals. For example, and without limitation, signal transformation component 408 may be configured to perform one or more operations such as preprocessing, lexical analysis, parsing, semantic analysis, and the like thereof. In an embodiment, and without limitation, signal transformation component 408 may include one or more analog-to-digital convertors that transform a first signal of an analog signal to a second signal of a digital signal. For example, and without limitation, an analog-to-digital converter may convert an analog input signal to a 10-bit binary digital representation of that signal. In another embodiment, signal transformation component 408 may include transforming one or more low-level languages such as, but not limited to, machine languages and/or assembly languages. For example, and without limitation, signal transformation component 408 may include transforming a binary language signal to an assembly language signal. In an embodiment, and without limitation, signal transformation component 408 may include transforming one or more high-level languages and/or formal languages such as but not limited to alphabets, strings, and/or languages. For example, and without limitation, high-level languages may include one or more system languages, scripting languages, domain-specific languages, visual languages, esoteric languages, and the like thereof. As a further non-limiting example, high-level languages may include one or more algebraic formula languages, business data languages, string and list languages, object-oriented languages, and the like thereof

Still referring to FIG. 4 , signal transformation component 408 may be configured to optimize an intermediate representation 412. As used in this disclosure an “intermediate representation” is a data structure and/or code that represents the input signal. Signal transformation component 408 may optimize intermediate representation as a function of a data-flow analysis, dependence analysis, alias analysis, pointer analysis, escape analysis, and the like thereof. In an embodiment, and without limitation, signal transformation component 408 may optimize intermediate representation 412 as a function of one or more inline expansions, dead code eliminations, constant propagation, loop transformations, and/or automatic parallelization functions. In another embodiment, signal transformation component 408 may optimize intermediate representation as a function of a machine dependent optimization such as a peephole optimization, wherein a peephole optimization may rewrite short sequences of code into more efficient sequences of code. Signal transformation component 408 may optimize intermediate representation to generate an output language, wherein an “output language,” as used herein, is the native machine language of flight controller 404. For example, and without limitation, native machine language may include one or more binary and/or numerical languages.

In an embodiment, and without limitation, signal transformation component 408 may include transform one or more inputs and outputs as a function of an error correction code. An error correction code, also known as error correcting code (ECC), is an encoding of a message or lot of data using redundant information, permitting recovery of corrupted data. An ECC may include a block code, in which information is encoded on fixed-size packets and/or blocks of data elements such as symbols of predetermined size, bits, or the like. Reed-Solomon coding, in which message symbols within a symbol set having q symbols are encoded as coefficients of a polynomial of degree less than or equal to a natural number k, over a finite field F with q elements; strings so encoded have a minimum hamming distance of k+1, and permit correction of (q−k−1)/2 erroneous symbols. Block code may alternatively or additionally be implemented using Golay coding, also known as binary Golay coding, Bose-Chaudhuri, Hocquenghuem (BCH) coding, multidimensional parity-check coding, and/or Hamming codes. An ECC may alternatively or additionally be based on a convolutional code.

In an embodiment, and still referring to FIG. 4 , flight controller 404 may include a reconfigurable hardware platform 416. A “reconfigurable hardware platform,” as used herein, is a component and/or unit of hardware that may be reprogrammed, such that, for instance, a data path between elements such as logic gates or other digital circuit elements may be modified to change an algorithm, state, logical sequence, or the like of the component and/or unit. This may be accomplished with such flexible high-speed computing fabrics as field-programmable gate arrays (FPGAs), which may include a grid of interconnected logic gates, connections between which may be severed and/or restored to program in modified logic. Reconfigurable hardware platform 416 may be reconfigured to enact any algorithm and/or algorithm selection process received from another computing device and/or created using machine-learning processes.

Still referring to FIG. 4 , reconfigurable hardware platform 416 may include a logic component 420. As used in this disclosure a “logic component” is a component that executes instructions on output language. For example, and without limitation, logic component may perform basic arithmetic, logic, controlling, input/output operations, and the like thereof. Logic component 420 may include any suitable processor, such as without limitation a component incorporating logical circuitry for performing arithmetic and logical operations, such as an arithmetic and logic unit (ALU), which may be regulated with a state machine and directed by operational inputs from memory and/or sensors; logic component 420 may be organized according to Von Neumann and/or Harvard architecture as a non-limiting example. Logic component 420 may include, incorporate, and/or be incorporated in, without limitation, a microcontroller, microprocessor, digital signal processor (DSP), Field Programmable Gate Array (FPGA), Complex Programmable Logic Device (CPLD), Graphical Processing Unit (GPU), general purpose GPU, Tensor Processing Unit (TPU), analog or mixed signal processor, Trusted Platform Module (TPM), a floating point unit (FPU), and/or system on a chip (SoC). In an embodiment, logic component 420 may include one or more integrated circuit microprocessors, which may contain one or more central processing units, central processors, and/or main processors, on a single metal-oxide-semiconductor chip. Logic component 420 may be configured to execute a sequence of stored instructions to be performed on the output language and/or intermediate representation 412. Logic component 420 may be configured to fetch and/or retrieve the instruction from a memory cache, wherein a “memory cache,” as used in this disclosure, is a stored instruction set on flight controller 404. Logic component 420 may be configured to decode the instruction retrieved from the memory cache to opcodes and/or operands. Logic component 420 may be configured to execute the instruction on intermediate representation 412 and/or output language. For example, and without limitation, logic component 420 may be configured to execute an addition operation on intermediate representation 412 and/or output language.

In an embodiment, and without limitation, logic component 420 may be configured to calculate a flight element 424. As used in this disclosure a “flight element” is an element of datum denoting a relative status of aircraft. For example, and without limitation, flight element 424 may denote one or more torques, thrusts, airspeed velocities, forces, altitudes, groundspeed velocities, directions during flight, directions facing, forces, orientations, and the like thereof. For example, and without limitation, flight element 424 may denote that aircraft is cruising at an altitude and/or with a sufficient magnitude of forward thrust. As a further non-limiting example, flight status may denote that is building thrust and/or groundspeed velocity in preparation for a takeoff. As a further non-limiting example, flight element 424 may denote that aircraft is following a flight path accurately and/or sufficiently.

Still referring to FIG. 4 , flight controller 404 may include a chipset component 428. As used in this disclosure a “chipset component” is a component that manages data flow. In an embodiment, and without limitation, chipset component 428 may include a northbridge data flow path, wherein the northbridge dataflow path may manage data flow from logic component 420 to a high-speed device and/or component, such as a RAM, graphics controller, and the like thereof. In another embodiment, and without limitation, chipset component 428 may include a southbridge data flow path, wherein the southbridge dataflow path may manage data flow from logic component 420 to lower-speed peripheral buses, such as a peripheral component interconnect (PCI), industry standard architecture (ICA), and the like thereof. In an embodiment, and without limitation, southbridge data flow path may include managing data flow between peripheral connections such as ethernet, USB, audio devices, and the like thereof. Additionally or alternatively, chipset component 428 may manage data flow between logic component 420, memory cache, and a flight component 432. As used in this disclosure a “flight component” is a portion of an aircraft that can be moved or adjusted to affect one or more flight elements. For example, flight component 432 may include a component used to affect the aircrafts' roll and pitch which may comprise one or more ailerons. As a further example, flight component 432 may include a rudder to control yaw of an aircraft. In an embodiment, chipset component 428 may be configured to communicate with a plurality of flight components as a function of flight element 424. For example, and without limitation, chipset component 428 may transmit to an aircraft rotor to reduce torque of a first lift propulsor and increase the forward thrust produced by a pusher component to perform a flight maneuver.

In an embodiment, and still referring to FIG. 4 , flight controller 404 may be configured generate an autonomous function. As used in this disclosure an “autonomous function” is a mode and/or function of flight controller 404 that controls aircraft automatically. For example, and without limitation, autonomous function may perform one or more aircraft maneuvers, take offs, landings, altitude adjustments, flight leveling adjustments, turns, climbs, and/or descents. As a further non-limiting example, autonomous function may adjust one or more airspeed velocities, thrusts, torques, and/or groundspeed velocities. As a further non-limiting example, autonomous function may perform one or more flight path corrections and/or flight path modifications as a function of flight element 424. In an embodiment, autonomous function may include one or more modes of autonomy such as, but not limited to, autonomous mode, semi-autonomous mode, and/or non-autonomous mode. As used in this disclosure “autonomous mode” is a mode that automatically adjusts and/or controls aircraft and/or the maneuvers of aircraft in its entirety. For example, autonomous mode may denote that flight controller 404 will adjust the aircraft. As used in this disclosure a “semi-autonomous mode” is a mode that automatically adjusts and/or controls a portion and/or section of aircraft. For example, and without limitation, semi-autonomous mode may denote that a pilot will control the propulsors, wherein flight controller 404 will control the ailerons and/or rudders. As used in this disclosure “non-autonomous mode” is a mode that denotes a pilot will control aircraft and/or maneuvers of aircraft in its entirety.

In an embodiment, and still referring to FIG. 4 , flight controller 404 may generate autonomous function as a function of an autonomous machine-learning model. As used in this disclosure an “autonomous machine-learning model” is a machine-learning model to produce an autonomous function output given flight element 424 and a pilot signal 436 as inputs; this is in contrast to a non-machine learning software program where the commands to be executed are determined in advance by a user and written in a programming language. As used in this disclosure a “pilot signal” is an element of datum representing one or more functions a pilot is controlling and/or adjusting. For example, pilot signal 436 may denote that a pilot is controlling and/or maneuvering ailerons, wherein the pilot is not in control of the rudders and/or propulsors. In an embodiment, pilot signal 436 may include an implicit signal and/or an explicit signal. For example, and without limitation, pilot signal 436 may include an explicit signal, wherein the pilot explicitly states there is a lack of control and/or desire for autonomous function. As a further non-limiting example, pilot signal 436 may include an explicit signal directing flight controller 404 to control and/or maintain a portion of aircraft, a portion of the flight plan, the entire aircraft, and/or the entire flight plan. As a further non-limiting example, pilot signal 436 may include an implicit signal, wherein flight controller 404 detects a lack of control such as by a malfunction, torque alteration, flight path deviation, and the like thereof. In an embodiment, and without limitation, pilot signal 436 may include one or more explicit signals to reduce torque, and/or one or more implicit signals that torque may be reduced due to reduction of airspeed velocity. In an embodiment, and without limitation, pilot signal 436 may include one or more local and/or global signals. For example, and without limitation, pilot signal 436 may include a local signal that is transmitted by a pilot and/or crew member. As a further non-limiting example, pilot signal 436 may include a global signal that is transmitted by air traffic control and/or one or more remote users that are in communication with the pilot of aircraft. In an embodiment, pilot signal 436 may be received as a function of a tri-state bus and/or multiplexor that denotes an explicit pilot signal should be transmitted prior to any implicit or global pilot signal.

Still referring to FIG. 4 , autonomous machine-learning model may include one or more autonomous machine-learning processes such as supervised, unsupervised, or reinforcement machine-learning processes that flight controller 404 and/or a remote device may or may not use in the generation of autonomous function. As used in this disclosure “remote device” is an external device to flight controller 404. Additionally or alternatively, autonomous machine-learning model may include one or more autonomous machine-learning processes that a field-programmable gate array (FPGA) may or may not use in the generation of autonomous function. Autonomous machine-learning process may include, without limitation machine learning processes such as simple linear regression, multiple linear regression, polynomial regression, support vector regression, ridge regression, lasso regression, elasticnet regression, decision tree regression, random forest regression, logistic regression, logistic classification, K-nearest neighbors, support vector machines, kernel support vector machines, naive bayes, decision tree classification, random forest classification, K-means clustering, hierarchical clustering, dimensionality reduction, principal component analysis, linear discriminant analysis, kernel principal component analysis, Q-learning, State Action Reward State Action (SARSA), Deep-Q network, Markov decision processes, Deep Deterministic Policy Gradient (DDPG), or the like thereof.

In an embodiment, and still referring to FIG. 4 , autonomous machine learning model may be trained as a function of autonomous training data, wherein autonomous training data may correlate a flight element, pilot signal, and/or simulation data to an autonomous function. For example, and without limitation, a flight element of an airspeed velocity, a pilot signal of limited and/or no control of propulsors, and a simulation data of required airspeed velocity to reach the destination may result in an autonomous function that includes a semi-autonomous mode to increase thrust of the propulsors. Autonomous training data may be received as a function of user-entered valuations of flight elements, pilot signals, simulation data, and/or autonomous functions. Flight controller 404 may receive autonomous training data by receiving correlations of flight element, pilot signal, and/or simulation data to an autonomous function that were previously received and/or determined during a previous iteration of generation of autonomous function. Autonomous training data may be received by one or more remote devices and/or FPGAs that at least correlate a flight element, pilot signal, and/or simulation data to an autonomous function. Autonomous training data may be received in the form of one or more user-entered correlations of a flight element, pilot signal, and/or simulation data to an autonomous function.

Still referring to FIG. 4 , flight controller 404 may receive autonomous machine-learning model from a remote device and/or FPGA that utilizes one or more autonomous machine learning processes, wherein a remote device and an FPGA is described above in detail. For example, and without limitation, a remote device may include a computing device, external device, processor, FPGA, microprocessor and the like thereof. Remote device and/or FPGA may perform the autonomous machine-learning process using autonomous training data to generate autonomous function and transmit the output to flight controller 404. Remote device and/or FPGA may transmit a signal, bit, datum, or parameter to flight controller 404 that at least relates to autonomous function. Additionally or alternatively, the remote device and/or FPGA may provide an updated machine-learning model. For example, and without limitation, an updated machine-learning model may be comprised of a firmware update, a software update, an autonomous machine-learning process correction, and the like thereof. As a non-limiting example a software update may incorporate a new simulation data that relates to a modified flight element. Additionally or alternatively, the updated machine learning model may be transmitted to the remote device and/or FPGA, wherein the remote device and/or FPGA may replace the autonomous machine-learning model with the updated machine-learning model and generate the autonomous function as a function of the flight element, pilot signal, and/or simulation data using the updated machine-learning model. The updated machine-learning model may be transmitted by the remote device and/or FPGA and received by flight controller 404 as a software update, firmware update, or corrected autonomous machine-learning model. For example, and without limitation autonomous machine learning model may utilize a neural net machine-learning process, wherein the updated machine-learning model may incorporate a gradient boosting machine-learning process.

Still referring to FIG. 4 , flight controller 404 may include, be included in, and/or communicate with a mobile device such as a mobile telephone or smartphone. Further, flight controller may communicate with one or more additional devices as described below in further detail via a network interface device. The network interface device may be utilized for commutatively connecting a flight controller to one or more of a variety of networks, and one or more devices. Examples of a network interface device include, but are not limited to, a network interface card (e.g., a mobile network interface card, a LAN card), a modem, and any combination thereof. Examples of a network include, but are not limited to, a wide area network (e.g., the Internet, an enterprise network), a local area network (e.g., a network associated with an office, a building, a campus or other relatively small geographic space), a telephone network, a data network associated with a telephone/voice provider (e.g., a mobile communications provider data and/or voice network), a direct connection between two computing devices, and any combinations thereof. The network may include any network topology and can may employ a wired and/or a wireless mode of communication.

In an embodiment, and still referring to FIG. 4 , flight controller 404 may include, but is not limited to, for example, a cluster of flight controllers in a first location and a second flight controller or cluster of flight controllers in a second location. Flight controller 404 may include one or more flight controllers dedicated to data storage, security, distribution of traffic for load balancing, and the like. Flight controller 404 may be configured to distribute one or more computing tasks as described below across a plurality of flight controllers, which may operate in parallel, in series, redundantly, or in any other manner used for distribution of tasks or memory between computing devices. For example, and without limitation, flight controller 404 may implement a control algorithm to distribute and/or command the plurality of flight controllers. As used in this disclosure a “control algorithm” is a finite sequence of well-defined computer implementable instructions that may determine the flight component of the plurality of flight components to be adjusted. For example, and without limitation, control algorithm may include one or more algorithms that reduce and/or prevent aviation asymmetry. As a further non-limiting example, control algorithms may include one or more models generated as a function of a software including, but not limited to Simulink by MathWorks, Natick, Massachusetts, USA. In an embodiment, and without limitation, control algorithm may be configured to generate an auto-code, wherein an “auto-code,” is used herein, is a code and/or algorithm that is generated as a function of the one or more models and/or software's. In another embodiment, control algorithm may be configured to produce a segmented control algorithm. As used in this disclosure a “segmented control algorithm” is control algorithm that has been separated and/or parsed into discrete sections. For example, and without limitation, segmented control algorithm may parse control algorithm into two or more segments, wherein each segment of control algorithm may be performed by one or more flight controllers operating on distinct flight components.

In an embodiment, and still referring to FIG. 4 , control algorithm may be configured to determine a segmentation boundary as a function of segmented control algorithm. As used in this disclosure a “segmentation boundary” is a limit and/or delineation associated with the segments of the segmented control algorithm. For example, and without limitation, segmentation boundary may denote that a segment in the control algorithm has a first starting section and/or a first ending section. As a further non-limiting example, segmentation boundary may include one or more boundaries associated with an ability of flight component 432. In an embodiment, control algorithm may be configured to create an optimized signal communication as a function of segmentation boundary. For example, and without limitation, optimized signal communication may include identifying the discrete timing required to transmit and/or receive the one or more segmentation boundaries. In an embodiment, and without limitation, creating optimized signal communication further comprises separating a plurality of signal codes across the plurality of flight controllers. For example, and without limitation the plurality of flight controllers may include one or more formal networks, wherein formal networks transmit data along an authority chain and/or are limited to task-related communications. As a further non-limiting example, communication network may include informal networks, wherein informal networks transmit data in any direction. In an embodiment, and without limitation, the plurality of flight controllers may include a chain path, wherein a “chain path,” as used herein, is a linear communication path comprising a hierarchy that data may flow through. In an embodiment, and without limitation, the plurality of flight controllers may include an all-channel path, wherein an “all-channel path,” as used herein, is a communication path that is not restricted to a particular direction. For example, and without limitation, data may be transmitted upward, downward, laterally, and the like thereof. In an embodiment, and without limitation, the plurality of flight controllers may include one or more neural networks that assign a weighted value to a transmitted datum. For example, and without limitation, a weighted value may be assigned as a function of one or more signals denoting that a flight component is malfunctioning and/or in a failure state.

Still referring to FIG. 4 , the plurality of flight controllers may include a master bus controller. As used in this disclosure a “master bus controller” is one or more devices and/or components that are connected to a bus to initiate a direct memory access transaction, wherein a bus is one or more terminals in a bus architecture. Master bus controller may communicate using synchronous and/or asynchronous bus control protocols. In an embodiment, master bus controller may include flight controller 404. In another embodiment, master bus controller may include one or more universal asynchronous receiver-transmitters (UART). For example, and without limitation, master bus controller may include one or more bus architectures that allow a bus to initiate a direct memory access transaction from one or more buses in the bus architectures. As a further non-limiting example, master bus controller may include one or more peripheral devices and/or components to communicate with another peripheral device and/or component and/or the master bus controller. In an embodiment, master bus controller may be configured to perform bus arbitration. As used in this disclosure “bus arbitration” is method and/or scheme to prevent multiple buses from attempting to communicate with and/or connect to master bus controller. For example and without limitation, bus arbitration may include one or more schemes such as a small computer interface system, wherein a small computer interface system is a set of standards for physical connecting and transferring data between peripheral devices and master bus controller by defining commands, protocols, electrical, optical, and/or logical interfaces. In an embodiment, master bus controller may receive intermediate representation 412 and/or output language from logic component 420, wherein output language may include one or more analog-to-digital conversions, low bit rate transmissions, message encryptions, digital signals, binary signals, logic signals, analog signals, and the like thereof described above in detail.

Still referring to FIG. 4 , master bus controller may communicate with a slave bus. As used in this disclosure a “slave bus” is one or more peripheral devices and/or components that initiate a bus transfer. For example, and without limitation, slave bus may receive one or more controls and/or asymmetric communications from master bus controller, wherein slave bus transfers data stored to master bus controller. In an embodiment, and without limitation, slave bus may include one or more internal buses, such as but not limited to a/an internal data bus, memory bus, system bus, front-side bus, and the like thereof. In another embodiment, and without limitation, slave bus may include one or more external buses such as external flight controllers, external computers, remote devices, printers, aircraft computer systems, flight control systems, and the like thereof.

In an embodiment, and still referring to FIG. 4 , control algorithm may optimize signal communication as a function of determining one or more discrete timings. For example, and without limitation master bus controller may synchronize timing of the segmented control algorithm by injecting high priority timing signals on a bus of the master bus control. As used in this disclosure a “high priority timing signal” is information denoting that the information is important. For example, and without limitation, high priority timing signal may denote that a section of control algorithm is of high priority and should be analyzed and/or transmitted prior to any other sections being analyzed and/or transmitted. In an embodiment, high priority timing signal may include one or more priority packets. As used in this disclosure a “priority packet” is a formatted unit of data that is communicated between the plurality of flight controllers. For example, and without limitation, priority packet may denote that a section of control algorithm should be used and/or is of greater priority than other sections.

Still referring to FIG. 4 , flight controller 404 may also be implemented using a “shared nothing” architecture in which data is cached at the worker, in an embodiment, this may enable scalability of aircraft and/or computing device. Flight controller 404 may include a distributer flight controller. As used in this disclosure a “distributer flight controller” is a component that adjusts and/or controls a plurality of flight components as a function of a plurality of flight controllers. For example, distributer flight controller may include a flight controller that communicates with a plurality of additional flight controllers and/or clusters of flight controllers. In an embodiment, distributed flight control may include one or more neural networks. For example, neural network also known as an artificial neural network, is a network of “nodes,” or data structures having one or more inputs, one or more outputs, and a function determining outputs based on inputs. Such nodes may be organized in a network, such as without limitation a convolutional neural network, including an input layer of nodes, one or more intermediate layers, and an output layer of nodes. Connections between nodes may be created via the process of “training” the network, in which elements from a training dataset are applied to the input nodes, a suitable training algorithm (such as Levenberg-Marquardt, conjugate gradient, simulated annealing, or other algorithms) is then used to adjust the connections and weights between nodes in adjacent layers of the neural network to produce the desired values at the output nodes. This process is sometimes referred to as deep learning.

Still referring to FIG. 4 , a node may include, without limitation a plurality of inputs x_(i) that may receive numerical values from inputs to a neural network containing the node and/or from other nodes. Node may perform a weighted sum of inputs using weights w_(i) that are multiplied by respective inputs x_(i). Additionally or alternatively, a bias b may be added to the weighted sum of the inputs such that an offset is added to each unit in the neural network layer that is independent of the input to the layer. The weighted sum may then be input into a function φ, which may generate one or more outputs y. Weight w_(i) applied to an input x_(i) may indicate whether the input is “excitatory,” indicating that it has strong influence on the one or more outputs y, for instance by the corresponding weight having a large numerical value, and/or a “inhibitory,” indicating it has a weak effect influence on the one more inputs y, for instance by the corresponding weight having a small numerical value. The values of weights w_(i) may be determined by training a neural network using training data, which may be performed using any suitable process as described above. In an embodiment, and without limitation, a neural network may receive semantic units as inputs and output vectors representing such semantic units according to weights w_(i) that are derived using machine-learning processes as described in this disclosure.

Still referring to FIG. 4 , flight controller may include a sub-controller 440. As used in this disclosure a “sub-controller” is a controller and/or component that is part of a distributed controller as described above; for instance, flight controller 404 may be and/or include a distributed flight controller made up of one or more sub-controllers. For example, and without limitation, sub-controller 440 may include any controllers and/or components thereof that are similar to distributed flight controller and/or flight controller as described above. Sub-controller 440 may include any component of any flight controller as described above. Sub-controller 440 may be implemented in any manner suitable for implementation of a flight controller as described above. As a further non-limiting example, sub-controller 440 may include one or more processors, logic components and/or computing devices capable of receiving, processing, and/or transmitting data across the distributed flight controller as described above. As a further non-limiting example, sub-controller 440 may include a controller that receives a signal from a first flight controller and/or first distributed flight controller component and transmits the signal to a plurality of additional sub-controllers and/or flight components.

Still referring to FIG. 4 , flight controller may include a co-controller 444. As used in this disclosure a “co-controller” is a controller and/or component that joins flight controller 404 as components and/or nodes of a distributer flight controller as described above. For example, and without limitation, co-controller 444 may include one or more controllers and/or components that are similar to flight controller 404. As a further non-limiting example, co-controller 444 may include any controller and/or component that joins flight controller 404 to distributer flight controller. As a further non-limiting example, co-controller 444 may include one or more processors, logic components and/or computing devices capable of receiving, processing, and/or transmitting data to and/or from flight controller 404 to distributed flight control system. Co-controller 444 may include any component of any flight controller as described above. Co-controller 444 may be implemented in any manner suitable for implementation of a flight controller as described above.

In an embodiment, and with continued reference to FIG. 4 , flight controller 404 may be designed and/or configured to perform any method, method step, or sequence of method steps in any embodiment described in this disclosure, in any order and with any degree of repetition. For instance, flight controller 404 may be configured to perform a single step or sequence repeatedly until a desired or commanded outcome is achieved; repetition of a step or a sequence of steps may be performed iteratively and/or recursively using outputs of previous repetitions as inputs to subsequent repetitions, aggregating inputs and/or outputs of repetitions to produce an aggregate result, reduction or decrement of one or more variables such as global variables, and/or division of a larger processing task into a set of iteratively addressed smaller processing tasks. Flight controller may perform any step or sequence of steps as described in this disclosure in parallel, such as simultaneously and/or substantially simultaneously performing a step two or more times using two or more parallel threads, processor cores, or the like; division of tasks between parallel threads and/or processes may be performed according to any protocol suitable for division of tasks between iterations. Persons skilled in the art, upon reviewing the entirety of this disclosure, will be aware of various ways in which steps, sequences of steps, processing tasks, and/or data may be subdivided, shared, or otherwise dealt with using iteration, recursion, and/or parallel processing.

It is to be noted that any one or more of the aspects and embodiments described herein may be conveniently implemented using one or more machines (e.g., one or more computing devices that are utilized as a user computing device for an electronic document, one or more server devices, such as a document server, etc.) programmed according to the teachings of the present specification, as will be apparent to those of ordinary skill in the computer art. Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those of ordinary skill in the software art. Aspects and implementations discussed above employing software and/or software modules may also include appropriate hardware for assisting in the implementation of the machine executable instructions of the software and/or software module.

Such software may be a computer program product that employs a machine-readable storage medium. A machine-readable storage medium may be any medium that is capable of storing and/or encoding a sequence of instructions for execution by a machine (e.g., a computing device) and that causes the machine to perform any one of the methodologies and/or embodiments described herein. Examples of a machine-readable storage medium include, but are not limited to, a magnetic disk, an optical disc (e.g., CD, CD-R, DVD, DVD-R, etc.), a magneto-optical disk, a read-only memory “ROM” device, a random access memory “RAM” device, a magnetic card, an optical card, a solid-state memory device, an EPROM, an EEPROM, and any combinations thereof. A machine-readable medium, as used herein, is intended to include a single medium as well as a collection of physically separate media, such as, for example, a collection of compact discs or one or more hard disk drives in combination with a computer memory. As used herein, a machine-readable storage medium does not include transitory forms of signal transmission.

Such software may also include information (e.g., data) carried as a data signal on a data carrier, such as a carrier wave. For example, machine-executable information may be included as a data-carrying signal embodied in a data carrier in which the signal encodes a sequence of instruction, or portion thereof, for execution by a machine (e.g., a computing device) and any related information (e.g., data structures and data) that causes the machine to perform any one of the methodologies and/or embodiments described herein.

Examples of a computing device include, but are not limited to, an electronic book reading device, a computer workstation, a terminal computer, a server computer, a handheld device (e.g., a tablet computer, a smartphone, etc.), a web appliance, a network router, a network switch, a network bridge, any machine capable of executing a sequence of instructions that specify an action to be taken by that machine, and any combinations thereof. In one example, a computing device may include and/or be included in a kiosk.

FIG. 5 shows a diagrammatic representation of one embodiment of a computing device in the exemplary form of a computer system 500 within which a set of instructions for causing a control system to perform any one or more of the aspects and/or methodologies of the present disclosure may be executed. It is also contemplated that multiple computing devices may be utilized to implement a specially configured set of instructions for causing one or more of the devices to perform any one or more of the aspects and/or methodologies of the present disclosure. Computer system 500 includes a processor 504 and a memory 508 that communicate with each other, and with other components, via a bus 512. Bus 512 may include any of several types of bus structures including, but not limited to, a memory bus, a memory controller, a peripheral bus, a local bus, and any combinations thereof, using any of a variety of bus architectures.

Processor 504 may include any suitable processor, such as without limitation a processor incorporating logical circuitry for performing arithmetic and logical operations, such as an arithmetic and logic unit (ALU), which may be regulated with a state machine and directed by operational inputs from memory and/or sensors; processor 504 may be organized according to Von Neumann and/or Harvard architecture as a non-limiting example. Processor 504 may include, incorporate, and/or be incorporated in, without limitation, a microcontroller, microprocessor, digital signal processor (DSP), Field Programmable Gate Array (FPGA), Complex Programmable Logic Device (CPLD), Graphical Processing Unit (GPU), general purpose GPU, Tensor Processing Unit (TPU), analog or mixed signal processor, Trusted Platform Module (TPM), a floating point unit (FPU), and/or system on a chip (SoC).

Memory 508 may include various components (e.g., machine-readable media) including, but not limited to, a random-access memory component, a read only component, and any combinations thereof. In one example, a basic input/output system 516 (BIOS), including basic routines that help to transfer information between elements within computer system 500, such as during start-up, may be stored in memory 508. Memory 508 may also include (e.g., stored on one or more machine-readable media) instructions (e.g., software) 520 embodying any one or more of the aspects and/or methodologies of the present disclosure. In another example, memory 508 may further include any number of program modules including, but not limited to, an operating system, one or more application programs, other program modules, program data, and any combinations thereof.

Computer system 500 may also include a storage device 524. Examples of a storage device (e.g., storage device 524) include, but are not limited to, a hard disk drive, a magnetic disk drive, an optical disc drive in combination with an optical medium, a solid-state memory device, and any combinations thereof. Storage device 524 may be connected to bus 512 by an appropriate interface (not shown). Example interfaces include, but are not limited to, SCSI, advanced technology attachment (ATA), serial ATA, universal serial bus (USB), IEEE 1394 (FIREWIRE), and any combinations thereof. In one example, storage device 524 (or one or more components thereof) may be removably interfaced with computer system 500 (e.g., via an external port connector (not shown)). Particularly, storage device 524 and an associated machine-readable medium 528 may provide nonvolatile and/or volatile storage of machine-readable instructions, data structures, program modules, and/or other data for computer system 500. In one example, software 520 may reside, completely or partially, within machine-readable medium 528. In another example, software 520 may reside, completely or partially, within processor 504.

Computer system 500 may also include an input device 532. In one example, a user of computer system 500 may enter commands and/or other information into computer system 500 via input device 532. Examples of an input device 532 include, but are not limited to, an alpha-numeric input device (e.g., a keyboard), a pointing device, a joystick, a gamepad, an audio input device (e.g., a microphone, a voice response system, etc.), a cursor control device (e.g., a mouse), a touchpad, an optical scanner, a video capture device (e.g., a still camera, a video camera), a touchscreen, and any combinations thereof. Input device 532 may be interfaced to bus 512 via any of a variety of interfaces (not shown) including, but not limited to, a serial interface, a parallel interface, a game port, a USB interface, a FIREWIRE interface, a direct interface to bus 512, and any combinations thereof. Input device 532 may include a touch screen interface that may be a part of or separate from display 536, discussed further below. Input device 532 may be utilized as a user selection device for selecting one or more graphical representations in a graphical interface as described above.

A user may also input commands and/or other information to computer system 500 via storage device 524 (e.g., a removable disk drive, a flash drive, etc.) and/or network interface device 540. A network interface device, such as network interface device 540, may be utilized for connecting computer system 500 to one or more of a variety of networks, such as network 544, and one or more remote devices 548 connected thereto. Examples of a network interface device include, but are not limited to, a network interface card (e.g., a mobile network interface card, a LAN card), a modem, and any combination thereof. Examples of a network include, but are not limited to, a wide area network (e.g., the Internet, an enterprise network), a local area network (e.g., a network associated with an office, a building, a campus or other relatively small geographic space), a telephone network, a data network associated with a telephone/voice provider (e.g., a mobile communications provider data and/or voice network), a direct connection between two computing devices, and any combinations thereof. A network, such as network 544, may employ a wired and/or a wireless mode of communication. In general, any network topology may be used. Information (e.g., data, software 520, etc.) may be communicated to and/or from computer system 500 via network interface device 540.

Computer system 500 may further include a video display adapter 552 for communicating a displayable image to a display device, such as display device 536. Examples of a display device include, but are not limited to, a liquid crystal display (LCD), a cathode ray tube (CRT), a plasma display, a light emitting diode (LED) display, and any combinations thereof. Display adapter 552 and display device 536 may be utilized in combination with processor 504 to provide graphical representations of aspects of the present disclosure. In addition to a display device, computer system 500 may include one or more other peripheral output devices including, but not limited to, an audio speaker, a printer, and any combinations thereof. Such peripheral output devices may be connected to bus 512 via a peripheral interface 556. Examples of a peripheral interface include, but are not limited to, a serial port, a USB connection, a FIREWIRE connection, a parallel connection, and any combinations thereof

The foregoing has been a detailed description of illustrative embodiments of the invention. Various modifications and additions can be made without departing from the spirit and scope of this invention. Features of each of the various embodiments described above may be combined with features of other described embodiments as appropriate in order to provide a multiplicity of feature combinations in associated new embodiments. Furthermore, while the foregoing describes a number of separate embodiments, what has been described herein is merely illustrative of the application of the principles of the present invention. Additionally, although particular methods herein may be illustrated and/or described as being performed in a specific order, the ordering is highly variable within ordinary skill to achieve systems and methods according to the present disclosure. Accordingly, this description is meant to be taken only by way of example, and not to otherwise limit the scope of this invention.

Exemplary embodiments have been disclosed above and illustrated in the accompanying drawings. It will be understood by those skilled in the art that various changes, omissions and additions may be made to that which is specifically disclosed herein without departing from the spirit and scope of the present invention. 

What is claimed is:
 1. A high voltage distribution system for an electric aircraft, the system comprising: at least a power source mechanically connected to an electric aircraft, wherein the at least a power source is configured to supply power to the electric aircraft; a flight component mechanically connected to the electric aircraft; and a high voltage distribution component comprising: a power source connection configured to electrically connect the at least a power source and the high voltage distribution component; a flight component connection configured to electrically connect the flight component and the high voltage distribution component; a controller, wherein the controller is configured to: control power to the at least a power source from an electric charger via the battery connection; and control electrical power to the flight component from the at least a power source via the flight component connection; and a multibus configured to supply power from the power source to the flight component.
 2. The system of claim 1, wherein the multibus comprises a ring bus.
 3. The system of claim 1, wherein the multibus comprises a mesh bus.
 4. The system of claim 1, wherein the controller comprises a flight controller.
 5. The system of claim 1, wherein the power source comprises a pack monitoring unit (PMU) configured to communicate a condition of the power source to the controller of the high voltage distribution component.
 6. The system of claim 1, wherein the PMU is configured to regulate the supply of power from the multibus to the flight component as a function of a battery temperature.
 7. The system of claim 1, wherein the high voltage distribution component includes a bus tie, wherein the bus tie is configured electrically connect a power supply from a second at least a power source to the flight component if the at least a power source malfunctions.
 8. The system of claim 1, wherein the electric aircraft comprises an electric vertical takeoff and landing (eVTOL) aircraft.
 9. The system of claim 1, wherein the flight component comprises at least a propulsor.
 10. The system of claim 1, wherein the flight component comprises at least a motor.
 11. A method for high voltage distribution for an electric aircraft, the method comprising: providing a high voltage distribution system, the high voltage distribution system comprising: at least a power source mechanically connected to an electric aircraft, wherein the at least a power source is configured to supply power to the electric aircraft; a flight component mechanically connected to the electric aircraft; and a high voltage distribution component comprising: a power source connection configured to electrically connect the at least a power source and the high voltage distribution component; a flight component connection configured to electrically connect the flight component and the high voltage distribution component; a controller, wherein the controller is configured to: control power to the at least a power source from an electric charger via the battery connection; and control electrical power to the flight component from the at least a power source via the flight component connection; and a multibus configured to supply power from the power source to the flight component; determining, by the controller, an actuating power input of the flight component; and supplying, by the high voltage distribution component, an actuating power correlated to the actuating power input to the flight component from the power source via a flight component connection between the high voltage distribution component and the flight component.
 12. The method of claim 11, wherein the multibus comprises a ring bus.
 13. The method of claim 11, wherein the multibus comprises a mesh bus.
 14. The method of claim 11, wherein the controller comprises a flight controller.
 15. The method of claim 11, further comprises communicating, by a pack monitoring unit (PMU) of the power source, a condition of the power source to the controller.
 16. The method of claim 15, further comprising regulating, by the PMU, the supply of power from the multibus to the flight component as a function of a battery temperature.
 17. The method of claim 11, electrically connecting, by a bus tie of the high voltage distribution component, to supply of power from a second at least a power source to the flight component if the at least a power source malfunctions.
 18. The method of claim 11, wherein the electric aircraft comprises an electric vertical takeoff and landing (eVTOL) aircraft.
 19. The method of claim 11, wherein the flight component comprises at least a propulsor.
 20. The method of claim 11, wherein the flight component comprises at least a motor. 